Managing data relocation in storage systems

ABSTRACT

A method is used in managing data relocation in storage systems. A request is received to write to a slice of storage tier in a data storage system where the slice is being relocated. The relocation of the slice includes copying data of the slice to another slice in the data storage system. Location within the slice at which the request to write to the slice has been received is determined. Based on the determination, relocation of the slice of the storage tier is effected.

BACKGROUND

Technical Field

This application relates to managing data relocation in storage systems.

Description of Related Art

A traditional storage array (herein also referred to as a “data storage system”, “disk storage array”, “disk array”, or simply “array”) is a collection of hard disk drives operating together logically as a unified storage device. Storage arrays are designed to store large quantities of data. Storage arrays typically include one or more storage array processors (SPs), for handling requests for allocation and input/output (I/O) requests. An SP is the controller for and primary interface to the storage array.

A storage array may be thought of as a system for managing a large amount of a resource, i.e., a large number of disk drives. Management of the resource may include allocation of a portion of the resource in response to allocation requests. In the storage array example, portions of the storage array may be allocated to, i.e., exclusively used by, entities that request such allocation.

The administrator of a storage array may desire to operate the array in a manner that maximizes throughput and minimizes response time. In general, performance of a storage array may be constrained by both physical and temporal constraints. Examples of physical constraints include bus occupancy and availability, excessive disk arm movement, and uneven distribution of load across disks. Examples of temporal constraints include bus bandwidth, bus speed, spindle rotational speed, serial versus parallel access to multiple read/write heads, and the size of data transfer buffers.

Large storage arrays today manage many disks that are not identical. Storage arrays use different types of disks and group the like kinds of disks into tiers based on the performance characteristics of the disks. A group of fast but small disks may be a fast tier (also referred to as “higher tier” or “high tier”). A group of slow but large disks may be a slow tier (also referred to as “lower tier” or “low tier”). It may be possible to have different tiers with different properties or constructed from a mix of different types of physical disks to achieve a performance or price goal. Storing often referenced, or hot, data on the fast tier and less often referenced, or cold, data on the slow tier may create a more favorable customer cost profile than storing all data on a single kind of disk.

A storage tier may be made up of different types of disks, i.e., disks with different redundant array of inexpensive disks (RAID) levels, performance and cost characteristics. In the industry there have become defined several levels of RAID systems. RAID (Redundant Array of Independent or Inexpensive Disks) parity schemes may be utilized to provide error detection during the transfer and retrieval of data across a storage system.

Data storage systems, such as disk drives, disk storage arrays, network storage devices, storage area networks, and the like, are called upon to store and manage a significant amount of data (e.g., gigabytes, terabytes, petabytes, etc.) that is written and read by many users. For example, a traditional storage array may include a collection of hard disk drives operating together logically as a unified storage device. Storage arrays are typically used to provide storage space for a plurality of computer file systems, databases, applications, and the like. For this and other reasons, it is common for physical storage arrays to be logically partitioned into chunks of storage space, called logical units, or LUs. This allows a unified storage array to appear as a collection of separate file systems, network drives, and/or volumes.

SUMMARY OF THE INVENTION

A method is used in managing data relocation in storage systems. A request is received to write to a slice of storage tier in a data storage system where the slice is being relocated. The relocation of the slice includes copying data of the slice to another slice in the data storage system. Location within the slice at which the request to write to the slice has been received is determined. Based on the determination, relocation of the slice of the storage tier is effected.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present technique will become more apparent from the following detailed description of exemplary embodiments thereof taken in conjunction with the accompanying drawings in which:

FIGS. 1-2 are examples of an embodiment of a computer system that may utilize the techniques described herein;

FIGS. 3, 4A, and 4B are examples illustrating storage device layout;

FIGS. 5-10 are block diagrams illustrating in more detail components that may be used in connection with techniques herein; and

FIG. 11 is a flow diagram illustrating processes that may be used in connection with techniques herein.

DETAILED DESCRIPTION OF EMBODIMENT(S)

Described below is a technique for use in managing data relocation in storage systems, which technique may be used to provide, among other things, receiving a request to write to a slice of storage tier in a data storage system, where the slice is being relocated, where relocation of the slice includes copying data of the slice to another slice in the data storage system, determining location within the slice at which the request to write to the slice has been received, based on the determination, effecting relocation of the slice of the storage tier.

Generally, a storage pool is a collection of storage that is provisioned for a logical unit. A storage pool may be a collection of disks, which may include disks of different types. Storage pools may further be subdivided into slices; for example a 1 gigabyte (GB) slice may be the allocation element for a logical unit. Further, a slice may be 256 megabytes (MB) in size. A pool may include a set of storage tiers. Further, both a storage tier and a pool may have storage devices of different performance capabilities and costs. A slice may be considered the smallest element that can be tracked and moved. It may be advantageous to store the hot or most accessed data on the devices within the storage pool with the best performance characteristics while storing the cold or least accessed data on the devices that have slower performance characteristics. This can lead to a lower cost system having both faster and slower devices that can emulate the performance of a more expensive system having only faster storage devices.

A storage tier or a storage pool may be a collection of storage containers. A storage container may be a unit of storage including a set of storage extents. A storage extent is a logical contiguous area of storage reserved for a user requesting the storage space. For example, a storage tier may include three storage containers, each storage container including a set of disks and the set of disk in each storage container having different RAID levels.

A disk may be a physical disk within the storage system. A LUN may be a logical unit number which is an identifier for a Logical Unit. Each slice of data may have a mapping to the location of the physical drive where it starts and ends.

Generally, slices are allocated to LUNs in a storage pool as “best-fit” at initial allocation time. In at least some cases, since the I/O load pattern of a slice is not known at initial allocation time, the performance capability of storage allocated may be too high or too low for effective data access on a slice. Furthermore, a data access pattern tends to change over time. Older data is accessed less frequently and therefore in at least many cases does not require storage with higher performance capability. Temperature of each storage slice is an indication of hotness of a slice, in other words, frequency and recency of slice I/Os. Better overall system performance can be achieved by placing hot slices to higher tier and cold slices to lower tier.

Slice relocation (herein also referred to as a “data relocation” or “data migration”) is a process of determining optimal or near optimal data placement among storage objects (e.g., storage tier, RAID group) based on I/O load of the storage objects. Slice relocation helps provide a way to determine respective preferable or best storage locations of slices within a LUN in a storage pool, and to construct a slice relocation candidate list to move slices from their current locations to the respective preferable or best locations. Data migration, i.e., the moving of data from one storage element to another, may be performed at the LUN level or at the slice level. Data migration at the slice level may be performed by copying the data of a slice and then updating an address map of the slice with the new location of the slice. A slice may store data or metadata of the data. I/O operations performed for copying data of a slice in order to relocate the slice are referred to as relocation I/Os. Generally, in order to perform data migration for a storage object such as a slice on which an I/O request from a host system is directed to at the time the slice is being relocated, the slice is mirrored in such a way that two copies of the slices are maintained during relocation of the slice where a source copy refers to the original slice which is targeted for relocation and a destination copy refers to a destination slice to which data of the original slice is copied to. Thus, data associated with a write I/O request directed to a portion of a slice which is in a process of being relocated is written to the slice and a destination slice which is mirrored to the slice.

Generally, an Auto-Tiering policy engine (PE) of a data storage system examines a storage pool's storage configuration and temperatures of all slices in that storage pool, and generates a slice relocation list. The slice relocation list identifies slices to be relocated with respective destination information. In general, slices in a storage pool are matched to the most appropriate respective tiers based on their respective temperatures (e.g., hot, cold) and tier preferences (e.g., High, Low, Optimal). If a slice's current tier differs from its matching tier, the slice is listed in the relocation candidate list. The PE is also referred to herein as the slice relocation process.

Further, a tiered storage pool may include storage with different performance characteristics such that a logical unit created from storage space provisioned from the storage pool may include slices from different storage tiers with different performance characteristics. An automated storage tiering process (also referred to herein simply as “slice relocation process”) relocates slices among storage tiers in order to improve I/O performance, decrease system runtime cost and reduce disk drive wear. However, the process of slice relocation consumes system resources such as CPU, memory, cache space, and bandwidth of a backend storage device. Thus, it may be desirable to efficiently relocate slices of a storage system.

Typically, when a slice receives a write I/O request from a host concurrent to relocation of the slice such that the slice is being relocated to a destination slice at that time, the write I/O request to mirrored to both the slice and destination slice such that data associated with the write I/O request is copied to both the slice and the destination slice.

In a conventional system, when a write I/O request is directed to a portion of slice which is being relocated, a conventional slice relocation process considers the complete slice as mirrored regardless of the location of the portion at which the write I/O request is directed to. Thus, in such a conventional system, when a write I/O request is directed to an offset of a slice which is mirrored to a destination slice because contents of the slice are in a process of being relocated, data associated with the write I/O request is copied to both the slice which is being relocated and the destination slice. Thus, in such a conventional system, for example, if a write I/O request is directed to an offset of 1000 bytes within a slice at the time the slice is being relocated to a destination slice, data associated with the write I/O request is copied at 1000 bytes offset within the slice and also copied at 1000 bytes offset within the destination slice even when the slice relocation process has only copied contents corresponding to the first 500 bytes of the slice to the destination slice thereby again copying the write I/O data at 1000 bytes offset by the slice relocation process. Thus, in such a conventional system, at least two I/O operations may be performed repetitively which un-necessarily may copy the same write I/O data again. Consequently, in such a conventional system, an additional I/O operation that may occur at overlapping portions within a slice reduces performance of a system by causing lock contentions. Further, in such a conventional system, additional data copy operations and rewriting host I/O data associated with a write I/O request increases backend system I/O load and reduces the number of concurrent operations that may be performed on a slice. As a result, in such a conventional system, copying each host I/O operation at two locations (first at a source slice and second at a destination slice) uses system resources such as CPU, adds load to a storage system, slows down the slice relocation process, and effects I/O load on a storage backend.

By contrast, in at least some implementations in accordance with the technique as described herein, the current technique tracks the location within a slice which indicates what portion of the slice has been relocated so far and based on the location and an offset at which a write I/O request is received, data associated with the write I/O request is either copied to both the slice and destination slice or only copied to the slice. Thus, in at least one embodiment of the current technique, tracking and managing a current data copy point within a slice which is being relocated enables the slice to be divided into two portion such that the first portion of the slice is considered mirrored in such a way that a write I/O request is copied to both the slice and destination slice, and the second portion of the slice is considered non-mirrored in such a way that a write I/O request is copied only to the slice thereby reducing the number of data copy operations and improving concurrency of operations performed on the slice.

Thus, in at least one embodiment of the current technique, if host I/O requests are directed to a location within a slice such that the location is ahead of the current data copy point indicating that the portion of slice including the location has not been relocated so far, data associated with the host I/O requests is only copied to the slice. Thus, in at least one embodiment of the current technique, a current data copy point of a slice logically apportions the slice into two portions; the first portion before the current data copy point is referred to as a mirrored range where a write I/O request is performed on the slice and the destination slice, and the second portion after the current data copy point is referred to as a non-mirrored range where a write I/O request is performed only on the slice. Thus, in at least one embodiment of the current technique, a current data copy point for a slice may be a pointer that points to a location within the slice which indicates a portion of the slice that has been copied to a destination slice so far. Generally, data is copied in chunks (e.g., a chunk of 100 kilobytes data) such that a current data copy point in a slice points to the end of a chunk that has been copied to a destination slice so far. A current data copy point of a slice is updated when contents of the previous chunk of the slice is copied to a destination slice. Thus, in at least one embodiment of the current technique, for example, if a slice includes 1024 data blocks and 100 of those data blocks have been copied to a destination slice indicating that the current data copy pointer points to 101th block, a write I/O request targeted at 500th data block is only copied to the slice and not to the destination slice because when the current data copy point of the slice reaches the 500^(th) data block, updated data is copied to the destination slice as part of relocating data of the slice.

In at least some implementations in accordance with the current technique as described herein, the use of the managing data relocation in storage systems technique can provide one or more of the following advantages: improving I/O performance of a slice relocation process by efficiently copying data associated with host I/O requests concurrent to the slice relocation process, improving overall performance of a storage system by enabling the storage system to efficiently manage relocation of slices while accommodating write I/O requests to the slices, and improving backend I/O load by reducing the number of host I/O write operations performed on slices that are being relocated.

Referring now to FIG. 1, shown is an example of an embodiment of a computer system that may be used in connection with performing the technique or techniques described herein. The computer system 10 includes one or more data storage systems 12 connected to host systems 14 a-14 n through communication medium 18. The system 10 also includes a management system 16 connected to one or more data storage systems 12 through communication medium 20. In this embodiment of the computer system 10, the management system 16, and the N servers or hosts 14 a-14 n may access the data storage systems 12, for example, in performing input/output (I/O) operations, data requests, and other operations. The communication medium 18 may be any one or more of a variety of networks or other type of communication connections as known to those skilled in the art. Each of the communication mediums 18 and 20 may be a network connection, bus, and/or other type of data link, such as hardwire or other connections known in the art. For example, the communication medium 18 may be the Internet, an intranet, network or other wireless or other hardwired connection(s) by which the host systems 14 a-14 n may access and communicate with the data storage systems 12, and may also communicate with other components (not shown) that may be included in the computer system 10. In at least one embodiment, the communication medium 20 may be a LAN connection and the communication medium 18 may be an iSCSI or fibre channel connection.

Each of the host systems 14 a-14 n and the data storage systems 12 included in the computer system 10 may be connected to the communication medium 18 by any one of a variety of connections as may be provided and supported in accordance with the type of communication medium 18. Similarly, the management system 16 may be connected to the communication medium 20 by any one of variety of connections in accordance with the type of communication medium 20. The processors included in the host computer systems 14 a-14 n and management system 16 may be any one of a variety of proprietary or commercially available single or multiprocessor system, such as an Intel-based processor, or other type of commercially available processor able to support traffic in accordance with each particular embodiment and application.

It should be noted that the particular examples of the hardware and software that may be included in the data storage systems 12 are described herein in more detail, and may vary with each particular embodiment. Each of the host computers 14 a-14 n, the management system 16 and data storage systems may all be located at the same physical site, or, alternatively, may also be located in different physical locations. In connection with communication mediums 18 and 20, a variety of different communication protocols may be used such as SCSI, Fibre Channel, iSCSI, FCoE and the like. Some or all of the connections by which the hosts, management system, and data storage system may be connected to their respective communication medium may pass through other communication devices, such as a Connectrix or other switching equipment that may exist such as a phone line, a repeater, a multiplexer or even a satellite. In at least one embodiment, the hosts may communicate with the data storage systems over an iSCSI or fibre channel connection and the management system may communicate with the data storage systems over a separate network connection using TCP/IP. It should be noted that although FIG. 1 illustrates communications between the hosts and data storage systems being over a first connection, and communications between the management system and the data storage systems being over a second different connection, an embodiment may also use the same connection. The particular type and number of connections may vary in accordance with particulars of each embodiment.

Each of the host computer systems may perform different types of data operations in accordance with different types of tasks. In the embodiment of FIG. 1, any one of the host computers 14 a-14 n may issue a data request to the data storage systems 12 to perform a data operation. For example, an application executing on one of the host computers 14 a-14 n may perform a read or write operation resulting in one or more data requests to the data storage systems 12.

The management system 16 may be used in connection with management of the data storage systems 12. The management system 16 may include hardware and/or software components. The management system 16 may include one or more computer processors connected to one or more I/O devices such as, for example, a display or other output device, and an input device such as, for example, a keyboard, mouse, and the like. A data storage system manager may, for example, view information about a current storage volume configuration on a display device of the management system 16. The manager may also configure a data storage system, for example, by using management software to define a logical grouping of logically defined devices, referred to elsewhere herein as a storage group (SG), and restrict access to the logical group.

It should be noted that although element 12 is illustrated as a single data storage system, such as a single data storage array, element 12 may also represent, for example, multiple data storage arrays alone, or in combination with, other data storage devices, systems, appliances, and/or components having suitable connectivity, such as in a SAN, in an embodiment using the techniques herein. It should also be noted that an embodiment may include data storage arrays or other components from one or more vendors. In subsequent examples illustrated the techniques herein, reference may be made to a single data storage array by a vendor, such as by EMC Corporation of Hopkinton, Mass. However, as will be appreciated by those skilled in the art, the techniques herein are applicable for use with other data storage arrays by other vendors and with other components than as described herein for purposes of example.

An embodiment of the data storage systems 12 may include one or more data storage systems. Each of the data storage systems may include one or more data storage devices, such as disks. One or more data storage systems may be manufactured by one or more different vendors. Each of the data storage systems included in 12 may be inter-connected (not shown). Additionally, the data storage systems may also be connected to the host systems through any one or more communication connections that may vary with each particular embodiment and device in accordance with the different protocols used in a particular embodiment. The type of communication connection used may vary with certain system parameters and requirements, such as those related to bandwidth and throughput required in accordance with a rate of I/O requests as may be issued by the host computer systems, for example, to the data storage systems 12.

It should be noted that each of the data storage systems may operate stand-alone, or may also included as part of a storage area network (SAN) that includes, for example, other components such as other data storage systems.

Each of the data storage systems of element 12 may include a plurality of disk devices or volumes. The particular data storage systems and examples as described herein for purposes of illustration should not be construed as a limitation. Other types of commercially available data storage systems, as well as processors and hardware controlling access to these particular devices, may also be included in an embodiment.

Servers or host systems, such as 14 a-14 n, provide data and access control information through channels to the storage systems, and the storage systems may also provide data to the host systems also through the channels. The host systems do not address the disk drives of the storage systems directly, but rather access to data may be provided to one or more host systems from what the host systems view as a plurality of logical devices or logical volumes. The logical volumes may or may not correspond to the actual disk drives. For example, one or more logical volumes may reside on a single physical disk drive. Data in a single storage system may be accessed by multiple hosts allowing the hosts to share the data residing therein. A LUN (logical unit number) may be used to refer to one of the foregoing logically defined devices or volumes. An address map kept by the storage array may associate host system logical address with physical device address.

In such an embodiment in which element 12 of FIG. 1 is implemented using one or more data storage systems, each of the data storage systems may include code thereon for performing the techniques as described herein. In following paragraphs, reference may be made to a particular embodiment such as, for example, an embodiment in which element 12 of FIG. 1 includes a single data storage system, multiple data storage systems, a data storage system having multiple storage processors, and the like. However, it will be appreciated by those skilled in the art that this is for purposes of illustration and should not be construed as a limitation of the techniques herein. As will be appreciated by those skilled in the art, the data storage system 12 may also include other components than as described for purposes of illustrating the techniques herein.

The data storage system 12 may include any one or more different types of disk devices such as, for example, an ATA disk drive, FC disk drive, and the like. Thus, the storage system may be made up of physical devices with different physical and performance characteristics (e.g., types of physical devices, disk speed such as in RPMs), RAID levels and configurations, allocation of cache, processors used to service an I/O request, and the like.

Given the different performance characteristics, one or more tiers of storage devices may be defined. The physical devices may be partitioned into tiers based on the performance characteristics of the devices; grouping similar performing devices together. An embodiment using the techniques herein may define a hierarchy of multiple tiers. Conversely, the particular performance characteristics may be applied to a storage pool with or without the definition of tiers. The set of resources associated with or designated for use by a tier or grouping within a pool may be characterized as a dynamic binding in that the particular set of data storage system resources utilized by consumers in a tier may vary from time to time. A current configuration for the data storage system, static aspects of the current data storage system resources (e.g., types of devices, device storage capacity and physical device characteristics related to speed and time to access data stored on the device), and current workload and other dynamic aspects (e.g., actual observed performance and utilization metrics) of the data storage system may vary at different points in time.

An Auto-Tiering policy engine (PE) of the data storage system 12 examines a storage pool's storage configuration and temperatures of all slices in that storage pool, and generates a slice relocation list. The slice relocation list identifies slices to be relocated with respective destination information. In general, slices in a storage pool are matched to the most appropriate respective tiers based on their respective temperatures (e.g., hot, cold) and tier preferences (e.g., High, Low, Optimal). If a slice's current tier differs from its matching tier, the slice is listed in the relocation candidate list. The PE is also referred to herein as the slice relocation process.

In certain cases, an enterprise can utilize different types of storage systems to form a complete data storage environment. In one arrangement, the enterprise can utilize both a block based storage system and a file based storage hardware, such as a VNX™ or VNXe™ system (produced by EMC Corporation, Hopkinton, Mass.). In such an arrangement, typically the file based storage hardware operates as a front-end to the block based storage system such that the file based storage hardware and the block based storage system form a unified storage system.

Referring now to FIG. 2, shown is an example of an embodiment of a computer system such as a unified data storage system that may be used in connection with performing the technique or techniques described herein. As shown, the unified data storage system 10 includes a block based storage system 12 and file based storage hardware 34. While the block based storage system 12 may be configured in a variety of ways, in at least one embodiment, the block based storage system 12 is configured as a storage area network (SAN), such as a VNX™ or VNXe™ system, as produced by EMC Corporation of Hopkinton, Mass. While the file based storage hardware 34 may be configured in a variety of ways, in at least one embodiment, the file based storage hardware 34 is configured as a network attached storage (NAS) system, such as a file server system produced by EMC Corporation of Hopkinton, Mass., configured as a header to the block based storage system 12.

The computer system 10 includes one or more block based data storage systems 12 connected to host systems 14 a-14 n through communication medium 18. The system 10 also includes a management system 16 connected to one or more block based data storage systems 12 through communication medium 20. In this embodiment of the computer system 10, the management system 16, and the N servers or hosts 14 a-14 n may access the block based data storage systems 12, for example, in performing input/output (I/O) operations, data requests, and other operations. The communication medium 18 may be any one or more of a variety of networks or other type of communication connections as known to those skilled in the art. Each of the communication mediums 18 and 20 may be a network connection, bus, and/or other type of data link, such as a hardwire or other connections known in the art. For example, the communication medium 18 may be the Internet, an intranet, network or other wireless or other hardwired connection(s) by which the host systems 14 a-14 n may access and communicate with the block based data storage systems 12, and may also communicate with other components (not shown) that may be included in the computer system 10. In one embodiment, the communication medium 20 may be a LAN connection and the communication medium 18 may be an iSCSI or fibre channel connection.

Each of the host systems 14 a-14 n and the block based data storage systems 12 included in the computer system 10 may be connected to the communication medium 18 by any one of a variety of connections as may be provided and supported in accordance with the type of communication medium 18. Similarly, the management system 16 may be connected to the communication medium 20 by any one of variety of connections in accordance with the type of communication medium 20. The processors included in the host computer systems 14 a-14 n and management system 16 may be any one of a variety of proprietary or commercially available single or multiprocessor system, such as an Intel-based processor, or other type of commercially available processor able to support traffic in accordance with each particular embodiment and application.

In at least one embodiment of the current technique, block based data storage system 12 includes multiple storage devices 40, which are typically hard disk drives, but which may be tape drives, flash memory, flash drives, other solid state drives, or some combination of the above. In at least one embodiment, the storage devices may be organized into multiple shelves 44, each shelf containing multiple devices. In the embodiment illustrated in FIG. 1, block based data storage system 12 includes two shelves, Shelf1 44A and Shelf2 44B; Shelf1 44A contains eight storage devices, D1-D8, and Shelf2 also contains eight storage devices, D9-D16.

Block based data storage system 12 may include one or more storage processors 46, for handling input/output (I/O) requests and allocations. Each storage processor 46 may communicate with storage devices 40 through one or more data buses 48. In at least one embodiment, block based data storage system 12 contains two storage processors, SP1 46A, and SP2 46B, and each storage processor 46 has a dedicated data bus 48 for each shelf 44. For example, SP1 46A is connected to each storage device 40 on Shelf1 44A via a first data bus 48A and to each storage device 40 on Shelf2 44B via a second data bus 48B. SP2 46B is connected to each storage device 40 on Shelf1 44A via a third data bus 48C and to each storage device 40 on Shelf2 44B via a fourth data bus 48D. In this manner, each device 40 is configured to be connected to two separate data buses 48, one to each storage processor 46. For example, storage devices D1-D8 may be connected to data buses 48A and 48C, while storage devices D9-D16 may be connected to data buses 48B and 48D. Thus, each device 40 is connected via some data bus to both SP1 46A and SP2 46B. The configuration of block based data storage system 12, as illustrated in FIG. 1, is for illustrative purposes only, and is not considered a limitation of the current technique described herein.

In addition to the physical configuration, storage devices 40 may also be logically configured. For example, multiple storage devices 40 may be organized into redundant array of inexpensive disks (RAID) groups. Although RAID groups are composed of multiple storage devices, a RAID group may be conceptually treated as if it were a single storage device. As used herein, the term “storage entity” may refer to either a single storage device or a RAID group operating as a single storage device.

Storage entities may be further sub-divided into logical units. A single RAID group or individual storage device may contain one or more logical units. Each logical unit may be further subdivided into portions of a logical unit, referred to as “slices”. In the embodiment illustrated in FIG. 1, storage devices D1-D5, is sub-divided into 3 logical units, LU1 42A, LU2 42B, and LU3 42C. The LUs 42 may be configured to store a data file as a set of blocks striped across the LUs 42.

The unified data storage system 10 includes a file based storage hardware 34 that includes at least one data processor 26. The data processor 26, for example, may be a commodity computer. The data processor 26 sends storage access requests through physical data link 36 between the data processor 26 and the block based storage system 12. The data link 36 may be any one or more of a variety of networks or other type of communication connections as known to those skilled in the art. The processor included in the data processor 26 may be any one of a variety of proprietary or commercially available single or multiprocessor system, such as an Intel-based processor, or other type of commercially available processor able to support traffic in accordance with each particular embodiment and application. Further, file based storage hardware 34 may further include control station 30 and additional data processors (such as data processor 27) sharing storage device 40. A dual-redundant data link 32 interconnects the data processors 26, 27 to the control station 30. The control station 30 monitors a heartbeat signal from each of the data processors 26, 27 in order to detect a data processor failure. If a failed data processor cannot be successfully re-booted, the control station 30 will “fence off” the failed data processor and re-assign or fail-over the data processing responsibilities of the failed data processor to another data processor of the file based storage hardware 34. The control station 30 also provides certain server configuration information to the data processors 26, 27. For example, the control station maintains a boot configuration file accessed by each data processor 26, 27 when the data processor is reset.

The data processor 26 is configured as one or more computerized devices, such as file servers, that provide end user devices (not shown) with networked access (e.g., NFS and CIFS facilities) to storage of the block based storage system 12. In at least one embodiment, the control station 30 is a computerized device having a controller, such as a memory and one or more processors. The control station 30 is configured to provide hardware and file system management, configuration, and maintenance capabilities to the data storage system 10. The control station 30 includes boot strap operating instructions, either as stored on a local storage device or as part of the controller that, when executed by the controller following connection of the data processor 26 to the block based storage system 12, causes the control station 30 to detect the automated nature of a file based storage hardware installation process and access the data processor 26 over a private internal management network and execute the file based hardware installation process.

Referring to FIG. 3, shown is an example representing how data storage system best practices may be used to form storage pools. The example 50 illustrates how storage pools may be constructed from groups of physical devices. For example, RAID Group1 64 a may be formed from physical devices 60 a. The data storage system best practices of a policy may specify the particular disks and configuration for the type of storage pool being formed. For example, for physical devices 60 a on a first data storage system type when forming a storage pool, RAID-5 may be used in a 4+1 configuration (e.g., 4 data drives and 1 parity drive). The RAID Group 1 64 a may provide a number of data storage LUNs 62 a. An embodiment may also utilize one or more additional logical device layers on top of the LUNs 62 a to form one or more logical device volumes 61 a. The particular additional logical device layers used, if any, may vary with the data storage system. It should be noted that there may not be a 1-1 correspondence between the LUNs of 62 a and the volumes of 61 a. In a similar manner, device volumes 61 b may be formed or configured from physical devices 60 b. The storage pool 1 of the example 50 illustrates two RAID groups being used to define a single storage pool although, more generally, one or more RAID groups may be used for form a storage pool in an embodiment using RAID techniques.

The data storage system 12 may also include one or more mapped devices 70-74. A mapped device (e.g., “thin logical unit”, “direct logical unit”) presents a logical storage space to one or more applications running on a host where different portions of the logical storage space may or may not have corresponding physical storage space associated therewith. However, the mapped device is not mapped directly to physical storage space. Instead, portions of the mapped storage device for which physical storage space exists are mapped to data devices such as device volumes 61 a-61 b, which are logical devices that map logical storage space of the data device to physical storage space on the physical devices 60 a-60 b. Thus, an access of the logical storage space of the mapped device results in either a null pointer (or equivalent) indicating that no corresponding physical storage space has yet been allocated, or results in a reference to a data device which in turn references the underlying physical storage space.

Referring to FIG. 4A, shown is a diagram illustrating an exemplary logical division of a storage of a data storage system into storage objects (such as RAID groups) for managing data relocation in the data storage system that may be included in an embodiment using the techniques described herein. With reference also to FIGS. 1-2, for example, storage entities 40 may refer to either a single storage device or a RAID group operating as a single storage device, may be further sub-divided into logical units. A single RAID group or individual storage device may contain one or more logical units (LUs) 40. However, RAID groups need not correspond to LUs and RAID groupings may be further divided into two or more LUs. In addition to RAID groups, each logical unit may be further subdivided into portions of a logical unit, referred to as “slices” 114. Slices 114 may be allocated, de-allocated, re-allocated, reserved, or redistributed by a slice manger. A slice may be, for example, a 1 GB slice of data. However, it should be noted that a slice may be any other size as well, such as 256 megabytes (MB). Further, the techniques described herein should not be construed as being limited to only slices of data; the techniques are equally applicable to other data chunk sizes, such as blocks, slivers (subset of slices), page, file or the like. The slice manager may be a software application or layer that is executed, at least in part, by one or more SPs 46. The slice manager may be responsible for implementing a slice allocation policy and/or algorithm. For example, the slice manager may receive slice allocation requests, and maintain relevant statistical information regarding slices.

Referring to FIG. 4B, shown is a diagram illustrating another example of logical division of a storage of a data storage system into storage objects (such as RAID groups, storage devices, slices) for managing data relocation in the data storage system that may be included in an embodiment using the techniques described herein. In at least one embodiment, a collection of hard disk drives may be organized into RAID arrays. The collective data storage capacity of storage devices (e.g., RG1 110A) is represented by data storage space. The data storage space may be divided into portions, hereinafter referred to as slices 114 (e.g., SLICE1-SLICE10). In at least one embodiment of the current technique, for example, each slice 114 is approximately 1 gigabyte (GB) in size, but other sizes may be used. Slices 114 within the data storage space may be organized into logical units (LUs), which are commonly referred to as LUNs.

In at least one embodiment of the current technique, data storage systems that comprise storage devices of varied performance characteristics grouped into tiers can be managed in such a way as to migrate data from one portion of the storage pool to another portion of the storage pool. A particular embodiment may help achieve this migration by automatically migrating data among the tiers based on the “temperature” of contents of a slice and location of the slice on storage devices. In general, temperature may correspond to, for example, how often and how recently the data is accessed. For example, hot data may refer to data that has been accessed recently and is accessed often, cold data may refer to data that has not been accessed recently and is not accessed often. Data temperature may be further segmented to include a warm data category that may include data that is less hot than hot data and/or less cold than cold data. Further, the temperature of a slice may be further adjusted based on the type of the slice indicating whether the slice stores data or metadata. Hence, warm data may refer to data that is accessed more often than cold data and less often that hot data. In general, in accordance with an embodiment of the current technique, hot data is migrated to faster (and typically more expensive) storage, and cold data is migrated to slower (and typically less expensive) storage. Warm data may be migrated to either type of storage and such storage may be configurable to be placed in a reduced power consumption state. Migration maybe accomplished by copying the data and changing the map entries for the logical addressed that were involved to reflect the new logical to physical association. Thus, hot data may be stored in disk drives indicated as hot disks and cold data may be stored in disk drives indicated as cold disks.

Additional details regarding slice relocation and tiered data storage arrays are disclosed in U.S. patent application Ser. No. 12/826,434, filed on Jun. 29, 2010 and entitled, “MANAGING MULTI-TIERED STORAGE POOL PROVISIONING” and U.S. patent application Ser. No. 12/824,816, filed on Jun. 28, 2010 and entitled, “METHODS, SYSTEMS, AND COMPUTER READABLE MEDIUM FOR TIER-BASED DATA STORAGE RESOURCE ALLOCATION AND DATA RELOCATION IN A DATA STORAGE ARRAY” which are incorporated by reference herein in their entireties.

Referring now to FIG. 5 that illustrates a process of relocating slices from a first storage tier of a storage pool to a second storage tier of the storage pool in a data storage system. In this figure, there are three storage tiers, Tier 1, Tier 2 and Tier 3. Each storage tier includes slices, such as slices 300, 310, and 320. As well, each slice has a temperature associated with it such as hot, cold, or medium. As well, some of the storage tier is also considered empty. Referring to the upper portion of the FIG. 5, there is a hot slice 310 in storage Tier 2. The temperature of a slice may be designated as a scalar or step value that is it may have a numerical equivalent such as 30 degrees or may simply be designated into a bucket, such as cold.

Also shown in the FIG. 5 is that Tier 1 has empty space 300. In this example, Tier 1 may have faster performance characteristics and a higher cost. Conversely, Tier 2 may have slower performance characteristics but a lower cost. This may be seen, for example, in the fact that there is more storage in Tier 2 than there is in Tier 1. Again, in the upper portion of the FIG. 5, it is shown that there is a hot slice 310 in Tier 2 that should be moved to Tier 1. In this example embodiment, as shown in the lower portion of FIG. 5, the hot slice is moved to Tier 1 leaving an empty space 340 in Tier 2.

Referring now to FIG. 6 that illustrates a process of relocating slices from a first storage tier of a storage pool to a second storage tier of the storage pool in a data storage system. In this embodiment, there is a hot slice 410 in Tier 2 and a medium slice 400 in Tier 1; however, Tier 1 has no space to accommodate an additional tier. Therefore, in this embodiment, the medium slice 400 on Tier 1 is migrated to Tier 2 and the hot slice 410 in Tier 2 is migrated to Tier 1. Note, that it was the need to migrate the hot slice 410 to Tier 1 that caused the medium slice 400 to be shifted to Tier 2. In this example, it may have been more effective to have the medium slice located in Tier 1. Also note that slices may change temperature based on data access request. Therefore, a slice's temperature may rise or fall over time. The slice's temperature may be the result of any number of calculations based on data access or data write requests to that slice.

Referring to FIG. 7, shown is more detailed example of an embodiment of a computer system that may be used in connection with performing the techniques described herein. With reference also to FIGS. 1-3, in a data storage system such as data storage system 12, a storage processor provides communications between host 14 and disk drives 60. Data storage system 12 includes at least two storage processors 46A, 46B. Both storage processor A (SPA) 46A and storage processor B (SPB) 46A provides access to Flare LUNs 105-108 built from a storage space provided by disk drives 60. Generally, a Flare LUN can only be accessed by one storage processor. Lower redirector 102 interacts with storage processors 46A, 46B to access Flare LUNs 105-108. The access to Flare LUNs 105-108 is independent of which storage processor each Flare LUN belongs to. A user of data storage system 12 allocates storage from Flare LUNs in fixed sized chunks. Each fixed size chunk is known as a slice. One or more slices are grouped together to create a slice pool. Host system 14 provisions storage from slice pools 100 for creating mapped LUNs 81-84. A mapped LUN is a LUN that is visible to host system 14 and a user of a data storage system. A mapped LUN may be a thin LUN (TLU) or a direct LUN (DLU). The size of a thin LUN is independent of amount of available storage. Typically, storage is allocated to a thin LUN when host system 14 issues a write request and needs a data block to write user's data. The size of a direct LUN is dependent of amount of available storage. Typically, storage is allocated to a direct LUN at the time the direct LUN is created and initialized. File system mapping driver 85 is a light-weight file system library that provides file system functionality and allows data storage system 12 to create files within a file system. File system mapping driver 85 processes I/Os directed to metadata of a file system. Mapped LUN driver 80 processes I/Os directed to data of the file system. Mapped LUN driver 80 also provides slices of storage from slice pools 100 to file system mapping driver 85 for creating a file system. Slices of storage can be dynamically added or removed by a file system. When a slice is removed, the file system redistributes data stored on the slice to other slices in the file system. File system mapping driver 85 allocates file system blocks from slices of storage for creating files and storing metadata of a file system. In at least some embodiments of the current technique, size of the file system block may be 8 kilobyte (KB) in size. A sparse volume concatenates slices of storage provided to file system mapping driver 85 into a logical contiguous address space on which a file system is created. The sparse volume maintains logical to physical mapping for slices of storage used to create the file system. Further, the file system maintains an allocation bitmap for every slice of physical storage that is used to create the file system. A mapped LUN presents a file as a LUN to host system 14. Further, the file presents a contiguous logical address space to the mapped LUN. For example, in FIG. 7, mapped LUN 81 presents file 86 as a LUN to host system 14, file 86 is created in a file system 90 and file system 90 is created from sparse volume 95. Similarly, mapped LUNs 82-84 presents file 87-89 as LUNs respectively to host system 14, files 87-89 are created in file systems 91-93 respectively and file systems 91-93 are created from sparse volumes 96-98 respectively. Further, sparse volumes 95-98 are created from slices of physical storage included in slice pools 100.

Referring to FIG. 8, shown is more detailed representation of a file system mapping driver 85 that may be included in an embodiment using the techniques herein. Sparse volume 95 aggregates one or more slices of physical storage together into a contiguous logical address space while some of these slices may or may not be provisioned. A provisioned slice has physical storage space allocated for storing data in the provisioned slice. For example, in FIG. 8, sparse volume 95 aggregates slices 125-134 together into a logical address space of 16 gigabyte (GB), where each slice is 1 gigabyte (GB) in size. However, it should be noted that each slice may be 256 megabyte (MB) in size. Root slice 125 and Slice-0 126 in a sparse volume is always provisioned, such that a storage space is available to store metadata information for slices included in the sparse volume 95. File system 90 is created from the contiguous logical address space provided by the sparse volume 95. A user of data storage system 12 creates files 86, 116-118 in file system 90. Each provisioned slice of a sparse volume has a corresponding configured slice object that is mapped to a corresponding LUN of physical storage included in device volumes 60. In at least some implementations, root slice 125 is stored in a data portion of slice-0 126, but for generality, the root slice is defined independently of the slice-0. Additionally, root slice 125 holds logical to physical address mapping for sparse volume 95.

At any given time, a storage space for a file system is either allocated (also referred to as provisioned) or not. If a storage space for a file system is not allocated, then there is said to be a hole at that location in a logical extent of the file system. For example, in FIG. 8, logical address space of sparse volume 95 has four holes 127, 130, 132, 133 indicating that slices corresponding to those locations are not provisioned.

Referring to FIG. 9, shown is a more detailed representation of components that may be included in an embodiment using the techniques described herein. In at least some embodiments of the current technique, a storage pool may include one or more RAID groups. A RAID group may be associated with data devices, such as the physical devices 60 a-60 b discussed herein, so that, for example, there is one or more data devices for each RAID group, any portion of a data device for any portion of the pools of storage, and/or any combinations thereof. Further, data devices associated with a storage pool may have different characteristics, such as speed, cost, reliability, availability, security and/or other characteristics. Further, storage pool 102 may include one or more storage tiers 458, 460, 462 such that each storage tier has different performance characteristics.

In at least one embodiment of the current technique, slice relocation manager 452 (also referred to as “Auto-Tiering policy engine (PE)”) may shift hot slices of a logical volume to upper tiers and cold slices of the logical volume down to lower tiers. The goal of the slice relocation process is to put hot, frequently accessed slices to higher tiers and maximize the utilization of these high tiers, which include faster but more expensive drives such as a flash storage drives. Slice relocation manager 452 relocates a slice based on the temperature of the slice. The temperature of a slice is determined based on I/O activity directed to the slice. I/O activity of a slice is an indicator of current I/O load of the slice. Slice I/O activity is computed using raw slice statistics. The computation may be done in any of several different ways. The specific computation to use may depend on the system I/O traffic pattern. In at least some cases, the simplest and most straightforward calculation is to use total slice I/O counts as I/O activity, such that the slice I/O load is the moving average of slice I/O counts.

In at least one embodiment of the current technique, slice relocation manager 452 works in conjunction with file system mapping driver 85 to relocate slices. Further, file system mapping driver 85 works in conjunction with mapped LUN driver 80 and sparse volume management logic 454 to relocate slices selected for relocation by slice relocation manager 452.

In at least one embodiment of the current technique, mapped LUN driver 80 receives an I/O request from data source 450 (e.g. a host system) to write data to a logical volume. Mapped LUN driver 80 sends a request to file system mapping driver 85 to receive information regarding a portion of a slice within the logical volume at which the data needs to be written. File system mapping driver 85 sends a request to sparse volume management logic 454 which first determines whether the slice is currently being relocated to a target slice. Based on the determination, sparse volume management logic 454 compares an offset indicating the location within the slice associated with the I/O request with the current position within the slice indicating a chunk of the slice which is currently being relocated. If the offset associated with the I/O request is before the current position for the slice relocation, data associated with the I/O request is copied to both the slice and target slice because the slice relocation process has already relocated data up to the current position such that the portion of slice before the current position needs to be in a mirrored state in order to successfully handle a failure condition during relocation of the slice. However, if the offset associated with the I/O request is after the current position for the slice relocation, data associated with the I/O request is copied only to the slice and not to the target slice because the slice relocation process is going to copy the portion of the slice which is after the current position as part of the slice relocation process. Thus, sparse volume management logic 454 determines a current position within a slice indicating how much data of the slice has been relocated by the slice relocation process and provides a set of extents to file system mapping driver 85 which in turn provides the set of extents to mapped LUN driver which writes data associated with host I/O requests to the set of extents. If mapped LUN driver 80 receives a single extent indicating a position within the slice at which data needs to be copied, the data is copied to the slice at the position indicated by the single extent. If mapped LUN driver 80 receives two extents indicating a primary slice and a target slice, the data is copied to both the primary and target slices at the position indicated by the set of extents.

Thus, in at least one embodiment of the current technique, sparse volume management logic 454 tracks a position within a slice when the slice is relocated to a target slice and determines whether to write data to both the slice and the target slice and an extent at which to write data associated with an I/O request. A range lock structure protects a chunk of a slice from being overwritten when the chunk of the slice is being relocated to a target slice during the time a host I/O request is received for the same chunk such that the host I/O request waits for the slice relocation process to finish relocating data of the chunk.

Referring to FIG. 10, shown is a more detailed representation of components that may be included in an embodiment using the techniques described herein. In at least one embodiment of the current technique, for example, a slice 465 is relocated to destination slice 466 by a slice relocation process. The slice relocation process copies data of the source slice 465 to the destination slice 466 by copying chunks of the data at a time. Copy point 467 tracks the position of a current chunk within source slice 465 indicating how much data of the source slice 465 has been copied so far by the slice relocation process. The portion of the source slice 465 before the copy point 467 is mirrored to the destination slice 466 in such a way that an I/O operation to the mirrored portion is performed on both source and destination slices 465, 466. The portion of the source slice 465 after the copy point 467 is not mirrored to the destination slice 466 such that an I/O operation to the non-mirrored portion is only performed on source slice 465.

For example, when a write I/O request A is received to write data at location 468, the location is compared with copy point 467. For example, in FIG. 10, the location 468 is prior to the copy point 467. In such a case, two extents (e.g., 468, 469) are provided to mapped LUN driver 80 for writing to both source and destination slices 465, 466. Further, for example, when a write I/O request B is received to write data at location 464, the location is compared with copy point 467. For example, in FIG. 10, the location 464 is after the copy point 467. In such a case, only one extent (e.g., 464) is provided to mapped LUN driver 80 for writing to only the source slice 465.

Referring to FIG. 11, shown is a more detailed flow diagram illustrating managing data relocation in storage systems (step 470). An I/O request is received for a slice which is being relocated to a target slice by a slice relocation process (step 472). A location within the slice at which the I/O request is directed to is evaluated (step 474). A determination is made as to whether the location is prior to a current copy location such that the current copy location indicates how much data of the slice has been relocated by the slice relocation process (step 476). If the location is prior to the current copy location, data associated with the I/O request is copied to both the slice and the target slice (step 478). However, if the location is after the current copy location, data associated with the I/O request is only copied to the slice and not to the target slice.

While the invention has been disclosed in connection with preferred embodiments shown and described in detail, their modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the spirit and scope of the present invention should be limited only by the following claims. 

What is claimed is:
 1. A method for use in managing data relocation in storage systems, the method comprising: receiving a request to write to a slice of storage tier in a data storage system, wherein the slice is being relocated, wherein relocation of the slice includes copying data of the slice to a target slice in the data storage system; determining location within the slice at which the request to write to the slice has been received, wherein the location is indicated by an offset within the slice; determining a current relocation position within the slice, wherein the current relocation position within the slice indicates a portion of slice that has been relocated to the target slice; based on the determination of the current relocation position and the location, writing data associated with the request to write to the slice to both the slice and the target slice upon determining that the location is before the current relocation position indicating that data of the slice up to the location has been relocated to the target slice; and based on the determination of the current relocation position and the location, writing data associated with the request to write to the slice to only the slice upon determining that the location is after the current relocation position indicating that the data of the slice from the current relocation position to the location has not been relocated to the target slice.
 2. The method of claim 1, further comprising: determining whether the location within the slice at which the request to write to the slice has been received is prior to a current copy point location, wherein the current copy location indicates a current position for a relocation process indicating how much data of the slice has been relocated.
 3. The method of claim 2, wherein effecting the relocation further comprising: based upon the determination, writing host data associated with the request to write to the slice to the slice at the location and writing the host data to the target slice at the location.
 4. The method of claim 2, wherein effecting the relocation further comprising: based upon the determination, writing host data associated with the request to write to the slice to the slice at the location.
 5. The method claim 1, wherein the request to write to the slice is received from a host.
 6. The method of claim 1, wherein a mapped LUN driver receives the request to write to the slice and sends the request to a file system mapping driver, wherein the file system mapping driver sends the request to a sparse volume management logic.
 7. The method of claim 6, wherein the sparse volume management logic provides primary and secondary write extents based on the determination of the location within the slice.
 8. The method of claim 6, wherein the sparse volume management logic provides a primary write extent based on the determination of the location within the slice.
 9. The method of claim 1, wherein the slice is a logical representation of a subset of physical disk storage.
 10. The method of claim 1, wherein the slice resides on the data storage system, wherein the data storage system includes a disk drive system comprising a plurality of Redundant Array of Inexpensive Disks (RAID) systems, each RAID system of the plurality of RAID systems having a first disk drive and a second disk drive.
 11. A system for use in managing data relocation in storage systems, the system comprising a processor configured to: receive a request to write to a slice of storage tier in a data storage system, wherein the slice is being relocated, wherein relocation of the slice includes copying data of the slice to a target slice in the data storage system; determine location within the slice at which the request to write to the slice has been received, wherein the location is indicated by an offset within the slice; determine a current relocation position within the slice, wherein the current relocation position within the slice indicates a portion of slice that has been relocated to the target slice; based on the determination of the current relocation position and the location, write data associated with the request to write to the slice to both the slice and the target slice upon determining that the location is before the current relocation position indicating that data of the slice up to the location has been relocated to the target slice; and based on the determination of the current relocation position and the location, write data associated with the request to write to the slice to only the slice upon determining that the location is after the current relocation position indicating that the data of the slice from the current relocation position to the location has not been relocated to the target slice.
 12. The system of claim 11, further comprising: determine whether the location within the slice at which the request to write to the slice has been received is prior to a current copy point location, wherein the current copy location indicates a current position for a relocation process indicating how much data of the slice has been relocated.
 13. The system of claim 12, wherein effect the relocation further comprising: based upon the determination, write host data associated with the request to write to the slice to the slice at the location and writing the host data to the target slice at the location.
 14. The system of claim 12, wherein effect the relocation further comprising: based upon the determination, write host data associated with the request to write to the slice to the slice at the location.
 15. The system claim 11, wherein the request to write to the slice is received from a host.
 16. The system of claim 11, wherein a mapped LUN driver receives the request to write to the slice and sends the request to a file system mapping driver, wherein the file system mapping driver sends the request to a sparse volume management logic.
 17. The system of claim 16, wherein the sparse volume management logic provides primary and secondary write extents based on the determination of the location within the slice.
 18. The system of claim 16, wherein the sparse volume management logic provides a primary write extent based on the determination of the location within the slice.
 19. The system of claim 11, wherein the slice is a logical representation of a subset of physical disk storage.
 20. The system of claim 11, wherein the slice resides on the data storage system, wherein the data storage system includes a disk drive system comprising a plurality of Redundant Array of Inexpensive Disks (RAID) systems, each RAID system of the plurality of RAID systems having a first disk drive and a second disk drive. 